Techniques to manage energy savings for interoperable radio access technology networks

ABSTRACT

Techniques to manage energy savings for interoperable radio access technology (RAT) networks are described. An apparatus may comprise a processing circuit to execute an energy management application to manage energy consumption for one or more RAT networks, the energy management application comprising a distributed energy management component operative to manage energy saving states for one or more network resources of a single RAT network, the distributed energy management component to receive one or more energy saving decision parameters from a network resource profile associated with a network resource of the single RAT network, determine whether to switch the network resource to one of multiple energy saving states based on the one or more energy saving decision parameters, and send an energy control directive to instruct the network resource to switch energy saving states. Other embodiments are described and claimed.

RELATED APPLICATION

This application claims priority to U.S. provisional patent application Ser. No. 61/481,024 titled “Advanced Wireless Communication Systems and Techniques” filed Apr. 29, 2011, and incorporated by reference herein in its entirety.

BACKGROUND

Cellular networks continuously upgrade equipment to keep pace with the insatiable demand of mobile users. This demand increases energy consumption by orders of magnitude. Increased energy consumption raises costs for mobile telecommunication operators and subscribers, and also leads to environmental damage. Solutions are needed to reduce energy consumption for cellular networks, both at a mobile device level and a network device level. It is with respect to these and other considerations that the present improvements have been needed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a mobile telecommunication system.

FIG. 2 illustrates an embodiment of a first apparatus.

FIG. 3 illustrates an embodiment of a state diagram.

FIG. 4 illustrates an embodiment of a first operating environment.

FIG. 5 illustrates an embodiment of a second apparatus.

FIG. 6 illustrates an embodiment of a second operating environment.

FIG. 7 illustrates an embodiment of a mobile telecommunication system.

FIG. 8 illustrates an embodiment of a third operating environment.

FIG. 9 illustrates an embodiment of a fourth operating environment.

FIG. 10 illustrates an embodiment of a fifth operating environment.

FIG. 11 illustrates an embodiment of a sixth operating environment.

FIG. 12 illustrates an embodiment of a first logic flow.

FIG. 13 illustrates an embodiment of a second logic flow.

FIG. 14 illustrates an embodiment of a computing architecture.

DETAILED DESCRIPTION

Various embodiments are directed to energy saving techniques for mobile telecommunication systems. Some embodiments are particularly directed to energy saving management techniques for a mobile telecommunication system comprising one or more radio access technology (RAT) networks. The energy saving management techniques may be used to manage underutilized network resources, such as during off-peak hours, by activating or deactivating them as necessary to reduce energy consumption while still fulfilling service levels required by mobile network users. In one embodiment, this activation/deactivation can be performed for a single RAT system. In one embodiment, this activation/deactivation can be performed for multiple interoperable RAT systems working together to find an optimal balance between energy consumption and service readiness. As a result, the embodiments can improve affordability, scalability, modularity, extendibility, or interoperability for an operator, device or network.

FIG. 1 illustrates a block diagram for mobile telecommunication system 100. The mobile telecommunication system 100 may comprise multiple interoperable RAT networks 102, 112. The RAT networks 102, 112 may generally refer to a cellular radio system that implements one or more network elements utilizing radio frequency (RF) transceivers to communicate electromagnetic representations of different types of information, including without limitation voice information, data information, and control information. Although FIG. 1 illustrates only two RAT networks 102, 112 for purposes of clarity, it may be appreciated that the mobile telecommunication system 100 may comprise more than two RAT networks as desired for a given implementation. The embodiments are not limited in this context.

Each of the RAT networks 102, 112 may implement a different cellular radio system. Examples of cellular radio systems offering voice and/or data communications suitable for use by the RAT networks 102, 112 may include without limitation Code Division Multiple Access (CDMA) systems, Global System for Mobile Communications (GSM) systems, North American Digital Cellular (NADC) systems, Time Division Multiple Access (TDMA) systems, Extended-TDMA (E-TDMA) systems, Narrowband Advanced Mobile Phone Service (NAMPS) systems, Wide-band CDMA (WCDMA), CDMA-2000, Universal Mobile Telephone System (UMTS) systems, UMTS Terrestrial Radio Access (UTRA) systems, Evolved UTRA (EUTRA) systems, Universal Terrestrial Radio Access Network (UTRAN) systems, Evolved UTRAN (EUTRAN) systems, GSM with General Packet Radio Service (GPRS) systems (GSM/GPRS), CDMA/1xRTT systems, Enhanced Data Rates for Global Evolution (EDGE) systems, GSM/EDGE Radio Access Network (GERAN) systems, Evolution Data Only or Evolution Data Optimized (EV-DO) systems, Evolution For Data and Voice (EV-DV) systems, High Speed Downlink Packet Access (HSDPA) systems, High Speed Uplink Packet Access (HSUPA), Long Term Evolution (LTE), LTE Advanced (LTE-A), and so forth. The embodiments, however, are not limited to these examples.

In various embodiments, the RAT networks 102, 112 may implement related cellular radio systems. For instance, the RAT networks 102, 112 may implement cellular radio systems as defined by the 3^(rd) Generation Partnership Project (3GPP) series of standards, such as GSM, GPRS, EDGE, UMTS, LTE, LTE-A, and so forth. As such, the RAT networks 102, 112 may be interoperable. Interoperable refers to the RAT networks 102, 112 supporting some level of network sharing between different network operators. Other related cellular radio systems may be used as well, such as those cellular radio systems defined by the International Telecommunication Union (ITU), the Institute of Electrical and Electronics Engineers (IEEE) (e.g., the IEEE 802.11, 802.16 and 802.20 families of network standards), and others.

Each RAT network 102, 112 may be implemented as a cellular radio system comprising one or more cells each serviced by at least one base station. A cell may refer to an area of radio coverage as defined by a transmission envelope created by one or more radio-frequency (RF) transceivers implemented by a base station for a cell. A base station is a wireless communications station installed at a fixed location and used to wirelessly communicate with one or more user equipment (UE).

In the illustrated embodiment shown in FIG. 1, the RAT network 102 may comprise multiple cells each having a base station 104-a to service one or more UE 106-b. For instance, at its current location the UE 106-1 may be serviced by the base station 104-2. Similarly, the RAT network 112 may comprise multiple cells each having a base station 114-c to service one or more UE 116-d. For instance, at its current location the UE 116-2 may be serviced by the base station 114-4. Examples of UE 106-b, 116-d may include without limitation a mobile electronic device, such as a cellular telephone, a smart phone, a tablet computer, a handheld computer, a laptop computer, and other mobile electronic devices, some of which are described with reference to FIG. 14. A particular implementation for base stations 104-a, 114-c may depend on a specific type of cellular radio system implemented for each RAT network 112, 120. For instance, assume the RAT network 102 is implemented as a GSM system, and the RAT network 112 is implemented as a UMTS system. In this case, each of the base stations 104-a may be implemented as a base transceiver station (BTS), and each of the base stations 114-c may be implemented as a Node B or evolved Node B (eNodeB or eNB).

It is worthy to note that “a” and “b” and “c” and similar designators as used herein are intended to be variables representing any positive integer. Thus, for example, if an implementation sets a value for a=5, then a complete set of base stations 104-a may include base stations 104-1, 104-2, 104-3, 104-4 and 104-5. The embodiments are not limited in this context.

The RAT networks 102, 112 may each be managed by an operation, administration, and maintenance (OAM) device 110, 120, respectively. The OAM devices 110, 120 may be generally arranged to automate network planning, configuration and optimization for the RAT networks 102, 112. In one embodiment, each RAT network 102, 112 may be managed by a separate OAM device 110, 120, respectively. In one embodiment, both RAT networks 102, 112 may be managed by a single OAM device 110 or 120. The embodiments are not limited in this context.

The RAT networks 102, 112 may implement various energy saving techniques to reduce energy consumption by individual network elements of the RAT networks 102, 112, thereby reducing overall energy consumption of the RAT networks 102, 112. For instance, the energy saving techniques may reduce service capabilities of the RAT network 102 to reduce its energy consumption while providing a back-up by the RAT network 112, and vice-versa. In one embodiment, for example, the energy saving techniques implemented for the RAT networks 102, 112 may minor those defined in 3GPP TR 32.834 version 3.0 titled “Study on OAM aspects of Inter-RAT energy Saving” published in August 2011 (“3GPP Energy Saving Specification”), as well as its revisions, progeny and variants.

When implementing energy saving techniques for a selected RAT network 102, 112, it may be appreciated that there may be a loss of service for any UE 106-b, 116-d currently operating within the selected RAT network 102, 112. This effect may be somewhat mitigated by using controlled hand-off techniques to hand-off the UE 106-b, 116-d to another RAT network. However, those UE 106-b, 116-d having weak connections may be lost. Further, a difference in service quality between RAT networks may be such that customer experience during energy saving may be degraded. These and other factors may be accounted for when deciding whether to implement energy saving techniques for a RAT network 102, 112.

The energy saving techniques may be implemented in a distributed or centralized manner. In one embodiment, for example, the energy saving techniques may be implemented in a distributed model by various network elements for the RAT networks 102, 112, such as by one or more of the base stations 104-a, 114-c, respectively. In one embodiment, for example, the energy saving techniques may be implemented in a centralized model by a single network element for each of the RAT networks 102, 112, such as the OAM devices 110, 120, respectively. In one embodiment, for example, the energy saving techniques may be implemented in a centralized manner by a single network element for both of the RAT networks 102, 112, such as one of the OAM devices 110, 120.

When implemented in a distributed model, a network element (e.g., a base station) for the RAT networks 102, 112 may download a network resource profile that detail conditions for the network element to enter or exit an energy saving mode. The network resource profile may include parameters representing thresholds for traffic loads, time schedules for when to enter or exit energy saving modes, capability constraints, location constraints, and so forth. The network element may compare these parameters with real-time values, and make energy saving decision based on the comparison results. The network element may then decide for itself when to enter or exit an energy saving mode.

When implemented in a centralized model, the various network elements for the RAT networks 102, 112 report information to a central network element, such as one or both of the OAM devices 110, 120. In this manner, the OAM devices 110, 120 may collect network level information, such as traffic loads for each RAT network 102, 112, a number of active UE 106-b, 116-d, neighboring cell information for potential standby cells of energy saving cells, network topology information, and so forth. The OAM devices 110, 120 may download or store a network resource profile associated with different network elements for the RAT networks 102, 112, with each network resource profile detailing conditions for an associated network element to enter or exit an energy saving mode. The network resource profile may include parameters representing thresholds for traffic loads, time schedules for when to enter or exit energy saving modes, capability constraints, location constraints, and so forth. The OAM devices 110, 120 may compare these parameters with real-time values, and make energy saving decision for individual network elements based on the comparison results. The OAM devices 110, 120 may then instruct the various network element as to when to enter or exit an energy saving mode.

FIG. 2 illustrates a block diagram of an apparatus 200. The apparatus 200 may illustrate an example of the energy saving techniques implemented in a distributed manner by various network elements for the RAT networks 102, 112. Although the apparatus 200 as shown in FIG. 2 has a limited number of elements in a certain topology, it may be appreciated that the apparatus 200 may include more or less elements in alternate topologies as desired for a given implementation.

In the illustrated embodiment shown in FIG. 2, the apparatus 200 comprises a processor circuit 218 and an energy management application 220. The energy management application 220 may be arranged for execution by the processor circuit 218 to manage energy consumption for one or more RAT networks 102, 112. The energy management application 220 may comprise, among other elements, a distributed energy management component 222 arranged to manage various energy saving states for one or more network resources of a single RAT network 102, 112.

A network resource may comprise any network element of the RAT networks 102, 112 that consumes power at a system level, device level, or component level, including without limitation the base stations 104-a, 114-c, the UE 106-b, 116-d, the OAM devices 110, 120, individual components (e.g., a processor, memory units, displays, RF transceivers, peripherals, etc.) of these devices, and other related network elements. The embodiments are not limited in this context.

The distributed energy management component 222 may receive one or more energy saving decision parameters 210-e from a network resource profile 208 associated with a network resource of the single RAT network 102, 112. The energy saving decision parameters 210-e may comprise any stored defined values useful for an energy saving decision, such as threshold values for triggering energy savings based on network conditions. For instance, assume an energy saving decision is made based on a current traffic load for one or both RAT networks 102, 112. In this case, an energy saving decision parameter 210-1 may comprise a threshold value representing a trigger point between a light and heavy traffic load for the RAT networks 102, 112. Different energy saving decision parameters 210-e may be stored in a network resource profile 208 associated with an individual network resource. In this manner, the energy management application 220 may have fine control when attempting to make energy saving decisions across the RAT networks 102, 112.

Examples for the energy saving decision parameters 210-e may include without limitation stored defined values for traffic load information, communication status information, channel status information, channel quality information (CQI), quality of service class indicator (QCI), signal-to-noise ratio (SNR), signal-to-interference ratio (SIR), signal-to-noise plus interference (SNIR), signal-to-noise and distortion ratio (SINAD), carrier-to-noise ratio (CNR), normalized signal-to-noise ratio (E_(b)/N₀), bit error rate (BER), packet error rate (PER), time information, date information, power consumption information, user equipment information, or standby RAT network information. The embodiments are not limited in this context.

The distributed energy management component 222 may determine whether to switch the network resource to one of multiple energy saving states based on the one or more energy saving decision parameters 210-e. For instance, the distributed energy management component 222 may receive one or more energy saving input values 212-f, compare the received energy saving input values 212-f with corresponding energy saving decision parameters 210-e from the network resource profile 208, and determine whether to switch the network resource to one of multiple energy saving states based on the comparison results.

The energy saving input values 212-f may comprise instantaneous real-time values received by the energy management application 220 and useful for comparison with the energy saving decision parameters 210-e to make an energy saving decision. Continuing with our previous example, assume an energy saving decision parameter 210-1 may comprise a threshold value representing a trigger point between a light and heavy traffic load for the RAT networks 102, 112. In this case, an energy saving input value 212-1 may comprise a statistical measure of a current traffic load over a defined time interval for one or both of the RAT networks 102, 112. If the energy saving input value 212-1 is less than (or equal to) the energy saving decision parameter 210-1, then the traffic load may be light enough to merit energy saving measures for one of the RAT networks 102, 112. However, if the energy saving input value 212-1 is greater than (or equal to) the energy saving decision parameter 210-1, then the traffic load may be heavy enough to maintain both of the RAT networks 102, 112 in fully-operational states.

Examples for the energy saving input values 212-f may roughly correspond to the stored defined values for the energy saving decision parameters 210-e, and therefore include without limitation real-time values for traffic load information, communication status information, channel status information, channel quality information (CQI), quality of service class indicator (QCI), signal-to-noise ratio (SNR), signal-to-interference ratio (SIR), signal-to-noise plus interference (SNIR), signal-to-noise and distortion ratio (SINAD), carrier-to-noise ratio (CNR), normalized signal-to-noise ratio (E_(b)/N₀), bit error rate (BER), packet error rate (PER), time information, date information, power consumption information, user equipment information, or standby RAT network information. The embodiments are not limited in this context.

The distributed energy management component 222 may send an energy control directive 230-g to instruct the network resource to switch energy saving states based on the determination results. Once the distributed energy management component 222 receives some minimum or maximum number of energy saving decision parameters 210-e and corresponding energy saving input values 212-f, the distributed energy management component 222 may run these values through an energy saving decision algorithm to make an energy saving decision for one or more network resources. The distributed energy management component 222 may then send an appropriate energy control directive 230-g to instruct the one or more network resource to switch energy saving states based on the determination results, as described in greater detail with reference to FIG. 3.

FIG. 3 illustrates an embodiment of a state diagram 300. The state diagram 300 illustrates different potential energy saving states for a network resource. As shown in the state diagram 300, a network resource may switch between an activated energy saving state 302 and a deactivated energy saving state 304. The activated energy saving state 302 is an energy saving state where a network resource is implementing energy saving measures and enters (or re-enters) a non-operational state where it is not consuming energy. The deactivated energy saving state 304 is an energy saving state where a network resource is not implementing any energy saving measures and therefore enters (or re-enters) an operational state where it is consuming energy.

The distributed energy management component 222 may control a given energy saving state for a given network resource via the energy control directives 230-g. For instance, a network resource may be communicatively coupled to the distributed energy management component 222 to receive an energy control directive 230-g, and change energy saving states in response to the energy control directive 230-g issued by the distributed energy management component 222. For instance, the distributed energy management component 222 may generate and send an activate energy control directive 230-1 to instruct a network resource to switch from a deactivated energy saving state 304 to an activated energy saving state 302. The distributed energy management component 222 may also generate and send a deactivate energy control directive 230-2 to instruct a network resource to switch from an activated energy saving state 302 to a deactivated energy saving state 304. In this manner, the distributed energy management component 222 may cycle various network resources for the RAT networks 102, 112 between energy saving states in response to instantaneous network conditions.

The network resources receiving the energy control directives 230-g do not necessarily need to switch energy saving states immediately upon receipt of the energy control directives 230-g. The network resources may delay switching energy saving states to allow time for controlled hand-offs of any UE 106-b, 116-d currently serviced by the network resource. The energy control directives 230-g may also have an associated time value indicating when the network resource should switch between energy saving states, such as in accordance with a network level schedule, for example. Further, the network resources may turn off any fault alarms when responding to explicit energy control directives 230-g.

Although the state diagram 300 only shows two energy saving states 302, 304 corresponding to a binary non-consumption or consumption of energy, respectively, it may be appreciated that various intermediate energy saving states may be defined corresponding to varying levels of energy consumption consistent with various power management techniques. For instance, the state diagram 300 may be modified to include various power states similar to those defined by the Advanced Configuration and Power Interface (ACPI) specification for computer systems, such as various global states, devices states, processor states, performance states, and so forth. Other power management techniques may be used as well. In this manner, the apparatus 200 may manage energy consumption by individual network resources or collective network resources of the RAT networks 102, 112 with a finer degree of granularity, such as placing a base station 104-a, 114-c in varying power saving modes ranging from a full power operational state, various intermediate power operational states (e.g., partial sleep mode, sleep mode, deep sleep mode, etc.), and a completely power-off operational state.

FIG. 4 illustrates an embodiment of an operating environment 400. The operating environment 400 shows the apparatus 200 as implemented by an exemplary base station 104-1 of the RAT network 102. The base station 104-1 is used by way of example and not limitation, and the apparatus 200 may be implemented with any of the base stations 104-a, 114-c of the respective RAT networks 102, 112 as desired for a given implementation. The embodiments are not limited in this context.

As shown in FIG. 4, the distributed energy management component 222 may generate an activate energy control directive 230-1 or a deactivate energy control directive 230-2 as described with reference to FIG. 3, and send the control directives 230-1, 230-2 to a network resource. In the operating environment 400, for example, a network resource may comprise one or more of base station platform components 402-i implemented by the base station 104-1. In one embodiment, for example, the base station platform components 402-i for the base station 104-1 may include without limitation a power supply 402-1, a radio frequency (RF) transceiver 402-2, and an antenna array 402-3, among others. Other possible base station platform components 402-i may be described with reference to FIG. 14. In this manner, the distributed energy management component 222 may cause the base station 104-1 to cycle between a full-power operational state and a no-power operational state in response to network conditions via the control directives 230-1, 230-2.

The distributed energy management component 222 may send a handoff control directive 240-1 to handoff UE 106-b from the RAT network 102 to a standby RAT network 112 prior to sending an energy control directive 230-g to instruct the network resource to switch energy saving states. In order to preserve on-going communications sessions with the UE 106-b currently within communication range of the base station 104-1, the distributed energy management component 222 may send a handoff control directive 240-1 to initiate hand-off operations for any active UE 106-b from the RAT network 102 to a standby RAT network 112 prior to sending an energy control directive 230-g to instruct the base station platform components 402-i to switch energy saving states. Alternatively, the distributed energy management component 222 may instruct the base station platform components 402-i to initiate hand-off operations per normal operations. Once hand-off operations are completed, the distributed energy management component 222 may then send a deactivate energy control directive 230-2 to instruct the network resource to switch to the deactivated energy saving state 304.

When the distributed energy management component 222 causes the base station 104-1 to enter a deactivated energy saving state 304, and the base station 104-1 is powered off, it may still preserve sufficient power to maintain operations of the energy management application 220. For instance, the processor circuit 218 may be powered by a secondary power supply or power rail separate from the power supply 402-1 of the base station platform components 402-i.

The distributed energy management component 222 may cycle between the activated energy saving state 302 and the deactivated energy saving state 304 as needed based on changing network conditions. However, a potential design consideration which may limit such cycles may be a time interval needed to switch between energy saving sates 302, 304. This design consideration may potentially limit a frequency for the cycles, and may be a factor considered by the distributed energy management component 222 when making energy saving decisions.

The distributed energy management component 222 may utilize an energy saving decision algorithm to evaluate a set of decision factors encoded by a set of energy saving decision parameters 210-e and reflected by the corresponding energy saving input values 212-f. In one embodiment, for example, the distributed energy management component 222 may receive an energy saving input value 212-1 comprising a traffic load value for the RAT network 102 (e.g., 49%) over a defined time period (e.g., minutes, hours, days, etc.), compare the traffic load value with an energy saving decision parameter 210-1 comprising a threshold value (e.g., 50% traffic load), and send an activate energy control directive 230-1 when the traffic load value is less than the threshold value (e.g., comparison results=TRUE), and a deactivate energy control directive 230-2 when the traffic load value is greater than the threshold value (e.g., comparison results=FALSE).

In one embodiment, for example, the distributed energy management component 222 may receive an energy saving input value 212-2 comprising a standby RAT network value representing a standby RAT network 112 for the RAT network 102.

In one embodiment, for example, the distributed energy management component 222 may also receive an energy saving input value 212-3 comprising a capability value representing an alternate RAT network 112 for the RAT network 102 that is compatible with UE 106-b currently or potentially operating with the RAT network 102. The distributed energy management component 222 may compare the standby RAT network value with the capability value, and send an activate energy control directive 230-1 when the standby RAT network value matches the capability value, and a deactivate energy control directive 230-2 when the standby RAT network value does not match the capability value.

In one embodiment, for example, the distributed energy management component 222 may receive an energy saving input value 212-4 comprising a communication value representing a communication state of the UE 106-b when the standby RAT network value matches the capability value, and send an activate energy control directive 230-1 when the communication value indicates an active communication state between the UE 106-b and the standby RAT network 112, and a deactivate energy control directive 230-2 when the communication value indicates a deactive communication state between the UE 106-b and the standby RAT network 112.

It may be appreciated that the distributed energy management component 222 may implement different energy saving decision algorithms utilizing additional or alternative decision factors when making an energy saving decision for the RAT networks 102, 112, as described further below. The embodiments are not limited in this context.

FIG. 5 illustrates an embodiment of an apparatus 500. The apparatus 500 may be similar to the apparatus 200 as described with reference to FIG. 2. In addition, apparatus 500 may provide an example of the energy saving techniques implemented in a centralized manner by a single network element for one or both of the RAT networks 102, 112.

In the illustrated embodiment shown in FIG. 5, the apparatus 500 may comprise a processor circuit 518 and an energy management application 524. The energy management application 524 may be executed by the processor circuit 518 to manage energy consumption for one or more RAT networks 102, 112. For instance, the energy management application 524 may comprise a centralized energy management component 524 arranged to manage energy saving states for one or more network resources of multiple interoperable RAT networks 102, 112.

Similar to the distributed energy management component 222, the centralized energy management component 524 may make energy saving decisions based on a set of energy saving decision parameters 210-e and corresponding energy saving input values 212-f for a single network resource. However, unlike the distributed energy management component 222, the centralized energy management component 524 may make such individual decisions using network level information. As such, the centralized energy management component 524 may make energy saving decisions within a greater framework of network conditions and operational states for other network resources within the RAT networks 102, 112. For instance, when attempting to make an energy saving decision for a first network resource such as a base station 104-1, the centralized energy management component 524 may consider an energy saving decision parameter 210-2 and corresponding energy saving input value 212-2 representing a current energy saving state of a second network resource such as a base station 104-2 in the RAT network 102. For example, the energy saving decision parameter 210-2 may indicate that the base station 104-2 should be in an activated energy saving state 302 before the base station 104-1 may enter a deactivated energy saving state 304, and the energy saving input value 212-2 may indicate that the base station 104-2 is currently in a deactivated energy saving state 304. As such, this comparison result would weigh against allowing the base station 104-1 to enter a deactivated energy saving state 304. By way of contrast, the distributed energy management component 222 may not necessarily have access to such network level information, particularly if the base stations 104-1, 104-2 are not adjacent to each other therefore making it difficult to take direct statistical measurements (e.g., radio signal strength) to assess an energy saving state 302, 304 of each other.

The centralized energy management component 524 may retrieve an energy saving schedule 526 for network resources of the multiple interoperable RAT networks 102, 112 that reflects such network level information. The energy saving schedule 526 may list when certain network resources for the RAT networks 102, 112 should be placed in an activated energy saving state 302 or a deactivated energy saving state 304. In this manner, the energy saving schedule 526 may provide a desired balance of service readiness and energy savings across the entire RAT networks 102, 112.

In accordance with the energy saving schedule 526, the centralized energy management component 524 may receive one or more energy saving decision parameters 210-e from a network resource profile 208 associated with a network resource of a single RAT network 102 or 112. The centralized energy management component 524 may also receive one or more energy saving input values 212-f corresponding to the energy saving decision parameters 210-e. The centralized energy management component 524 may perform comparison operations, and determine whether to switch the network resource to one of multiple energy saving states 302, 304 based on the comparison results. The centralized energy management component 524 may then send an energy control directive 230-1, 230-2 to instruct the network resource to switch between energy saving states 302, 304 according to the determined results.

FIG. 6 illustrates an embodiment of an operating environment 600. The operating environment 600 shows the apparatus 500 as implemented by an exemplary OAM device 110 of the RAT network 102. The OAM device 110 is used by way of example and not limitation, and the apparatus 500 may be implemented with one or both of the OAM devices 110, 120 of the respective RAT networks 102, 112 as desired for a given implementation. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 6, the OAM device 110 may implement the energy management application 220 with the centralized energy management component 524. As a network level device receiving information for many if not all of the network elements for the RAT networks 102, 112, the OAM device 110 may make individual energy saving decisions for particular network resources using the network level information. The OAM device 110 may then issue energy control directives 230-1, 230-2 to different base stations 104-a, 114-c. In turn, the base stations 104-a, 114-c may power-on or power-off some or all of the base station platform components 402-i, 602-j, respectively, to switch to an appropriate energy saving state 302, 304. Further, the centralized energy management component 524 may issue hand-off control directives 240-h, or alternatively cause base stations 104-a, 114-c to issue such hand-off control directives 240-h, prior to placing the different base stations 104-a, 114-c in a deactivated energy saving state 304.

FIG. 7 illustrates an embodiment of a mobile telecommunication system 700. The mobile telecommunication system 700 may be the same or similar to the mobile telecommunication system 100, and provides more details for the exemplary RAT networks 102, 112, OAM device 110 and base stations 104-1, 114-1.

More particularly, the mobile telecommunication system 700 illustrates a particular use scenario where the RAT network 102 is arranged to provide overlay/back-up coverage for the RAT network 112. In this role, the RAT network 102 does not take any energy saving measures, and therefore will always remain in a full-power operational state to provide services to the UE 106-b, 116-d. As such, the RAT network 102 may sometimes be referred to as a “standby RAT network” to signify its always-on operational state. By way of contrast, the RAT network 112 does take energy saving measures under the control of the OAM device 110, and as such, various network resources for the RAT network 112 may be switched between the activated energy saving state 302 and the deactivated energy saving state 304 to create a balance between energy savings and service-readiness across the RAT networks 102, 112.

In the illustrated embodiment shown in FIG. 7, the mobile telecommunication system 700 may comprise network elements of multiple RAT networks 102, 112. For instance, the mobile telecommunication system 700 may comprise a first base station 104-1 for a first cell 740 of a first RAT network 102. The first base station 104-1 may be arranged to always remain in a deactivated energy saving state 304. The mobile telecommunication system 700 may further comprise a second base station 114-1 for a second cell 750 of a second RAT network 112 interoperable with the first RAT network 102. The second base station 114-1 may be arranged to switch between an activated energy saving state 302 and a deactivated energy saving state 304.

The mobile telecommunication system 700 may further comprise an OAM 110 device communicatively coupled to the first and second base stations 104-1, 114-1 of the first and second cells 740, 750, respectively. The OAM device 110 may comprise a processor circuit 518 and an energy management application 220. The energy management application 220 may comprise a centralized energy management component 222 (shown in FIG. 5) operative on the processor circuit 518 to receive one or more energy saving decision parameters 210-e from a network resource profile 208 associated with the second base station 114-1 for the second cell 750, determine whether to switch the second base station 114-1 to the activated energy saving state 302 or the deactivated energy saving state 304 based on the one or more energy saving decision parameters 210-e, and send an energy control directive 230-g to instruct the second base station 114-1 to switch to the activated energy saving state 302 or the deactivated energy saving state 304 based on the determination results.

The first base station 104-1 may have a first RF transceiver 706 coupled to a first antenna array 710 arranged to send and receive electromagnetic representations of information within a first transmission envelope 712. The second base station 114-1 may have a second RF transceiver 726 coupled to a second antenna array 730 arranged to send and receive electromagnetic representations of information within a second transmission envelope 732. The first and second transmission envelopes 712, 732 may partially or fully overlap each other.

The first and second cells 740, 750 may implement any combination of different cellular radio systems. In one embodiment, for example, the first cell 740 may comprise a GSM cell, and the second cell 750 may comprise a UMTS cell. In one embodiment, for example, the first cell 740 may comprise a GSM cell, and the second cell 750 may comprise a LTE cell. In one embodiment, for example, the first cell 740 may comprise a UMTS cell, and the second cell 750 may comprise a LTE cell. In one embodiment, for example, the first cell 740 may comprise a CDMA2000 cell, and the second cell 750 may comprise a LTE cell. These are merely a few examples of suitable combinations, and other combinations exist as well. The embodiments are not limited in this context.

The energy management application 220 of the OAM device 110 may make energy saving decisions for the base stations 104-1, 114-1 based on several factors as encoded in the energy saving decision parameters 210-e. Some of those factors may include, among other factors, a current traffic load for the RAT network 112, an availability of a standby cell 740 for the cell 750, a device capability constraint for UE 116-d currently operating within the cell 750, and a device location constraint for UE 116-d relative to the cell 750 which affects whether a UE 116-d may communicate with the standby cell 740. Such energy saving decisions may be described in more detail with reference to FIGS. 8-11.

FIG. 8 illustrates an embodiment of an operating environment 800. The operating environment 800 illustrates an exemplary use scenario for the centralized energy management component 524 utilizing an energy saving decision algorithm with multiple decision factors, including an exemplary UE capability constraint.

As shown in operating environment 800, the operating environment 800 illustrates multiple over-lapping cells for different interoperable RAT networks 812, 814 and 816, each having a pair of cells. The RAT networks 812, 814 and 816 may co-locate certain equipment, such as RF transceivers of base stations, for each of the RAT networks 812, 814 and 816 on a same cellular tower 850.

In this use scenario, assume a first RAT network 812 comprises a GSM network having GSM cells 810-1, 810-2, a second RAT network 814 comprises a UMTS network having UMTS cells 820-1, 820-2, and a third RAT network 816 comprises a LTE cell having LTE cells 830-1, 830-2. The RAT networks 812, 814 and 816 are interoperable in the sense that all three networks are designed using a same or similar set of standards following a same evolutionary path, where the GSM network is a second generation (2G) network, the UMTS network is a third generation (3G) network evolved from GSM, and the LTE network (or LTE-A) is a fourth generation (4G) network evolved from GSM and/or UMTS.

Mobile devices (or UE) may be designed to operate with each of the RAT networks 812, 814 and 816. For instance, the UE 802-k may be GSM devices designed to operate with the GSM network 812, the UE 804-l may be UMTS devices designed to operate with the UMTS network 814, and the UE 806-m may be LTE devices designed to operate with the LTE network 816. Furthermore, some or all of the UE 802-k, 804-l, 806-m may be “dual-mode” mobile devices capable of operating with more than one network. This is a typical scenario to allow redundant coverage for mobile devices to allow operations when portions of a network have been upgraded with more advanced cellular technologies (e.g., 3G or 4G), while other portions of the network have not (e.g., 2G). For instance, assume the UE 804-l, 806-m may be designed to also operate with the GSM network 812 in addition to the UMTS network 814 and the LTE network 816, respectively.

This use scenario may be used to demonstrate when the energy management application 220 of the OAM device 110 makes an energy saving decision for one or more base stations of the RAT networks 812, 814 and 816 based on several factors as encoded in the energy saving decision parameters 210-e, including a current traffic load for the RAT network 112, an availability of a standby cell 740 for the cell 750, and a device capability constraint for UE 116-d currently operating within the cell 750.

For instance, assume that the energy management application 220 receives an energy decision parameter 210-1 and an energy saving input value 212-1 to check a traffic load constraint for an energy saving decision algorithm. Assuming a current traffic load is lower than the threshold value, the centralized energy management component 524 may decide that one or more of the UMTS cells 820-1, 820-2 of the UMTS network 814 and/or the LTE cells 830-1, 830-2 of the LTE network 816 may be potential candidate for energy savings. In this role, the UMTS cells 820-1, 820-2 of the UMTS network 814 and/or the LTE cells 830-1, 830-2 of the LTE network 816 may be referred to herein as “energy saving cells.”

The centralized energy management component 524 may then check to see if the UMTS cells 820-1, 820-2 and/or the LTE cells 830-1, 830-2 have an available standby cell. In this case, since the GSM cells 810-1, 810-2 fully overlap the other cells, and are compatible with the UMTS network 814 and LTE network 816, the centralized energy management component 524 may receive an energy decision parameter 210-2 and an energy saving input value 212-2 to check a standby cell constraint for the energy saving decision algorithm. In this role, the GSM cells 810-1, 810-2 may be referred to herein as “standby cells.”

Additionally or alternatively, the UMTS cells 820-1, 820-2 of the UMTS network 814 and/or the LTE cells 830-1, 830-2 of the LTE network 816 may be referred to as a “RAT 1 Cell” using terminology consistent with the 3GPP Energy Saving Specification. The GSM cells 810-1, 810-2 may be referred to as “RAT 2 Cell” using terminology consistent with the 3GPP Energy Saving Specification. A RAT 1 Cell provides basic service coverage, while a RAT 2 Cell provides additional capacity and/or different services or service quality at specific locations.

The centralized energy management component 524 may finally check equipment capabilities for the UE 804-l, 806-m to see if some or all of the UE 804-l, 806-m are capable of operating with the GSM cells 810-1, 810-2. Since the UE 804-l, 806-m are dual-mode mobile devices capable of communicating with the GSM cells 810-1, 810-2 in a second mode, the centralized energy management component 524 may receive an energy decision parameter 210-3 and an energy saving input value 212-3 to check a UE capability constraint for the energy saving decision algorithm.

When all three conditions for the traffic load constraint, standby cell constraint and UE capability constraint are TRUE, the centralized energy management component 524 may issue an activate energy control directive 230-1 to power management components 714 of one or more base stations of the UMTS network 814 and/or the LTE network 816 to enter an activated energy saving state 302. When one of the three conditions is FALSE, and the base stations of the UMT network 814 and/or the LTE network 816 are in a deactivated energy saving state 304, the centralized energy management component 524 may do nothing and leave the UMT network 814 and/or the LTE network 816 in a deactivated energy saving state 304 until all three conditions turn TRUE. When one of the three conditions is FALSE, and the base stations of the UMT network 814 and/or the LTE network 816 are already in an activated energy saving state 302, the centralized energy management component 524 may issue a deactivate energy control directive 230-2 to the power management components 714 of one or more base stations of the UMT network 814 and/or the LTE network 816 to enter a deactivated energy saving state 304 until all three conditions turn TRUE again. For instance, if a traffic load for a RAT network having a network resource in an activated energy saving state 302 rises to above a threshold value, the network resource may be placed in deactivated energy saving state 304 to support the increased traffic loads.

FIG. 9 illustrates an embodiment of an operating environment 900. The operating environment 900 is similar to the operating environment 800 as described with reference to FIG. 8. The operating environment 900 illustrates an exemplary use scenario for the centralized energy management component 524 utilizing an energy saving decision algorithm with multiple decision factors, including an exemplary UE location constraint.

This use scenario may be used to demonstrate when the energy management application 220 of the OAM device 110 makes an energy saving decision for one or more base stations of the RAT networks 812, 814 and 816 based on several factors as encoded in the energy saving decision parameters 210-e, including a current traffic load for the RAT network 112, an availability of a standby cell 740 for the cell 750, a device capability constraint for UE 116-d currently operating within the cell 750, and a device location constraint for UE 804-1 operating in the UMTS cell 820-1 which affects whether a UE 804-1 may communicate with the standby GSM cell 810-1.

As described with the operating environment 800, the centralized energy management component 524 may check the traffic load constraint, standby cell constraint and UE capability constraint for the UE 804-l, 806-m. In addition, the centralized energy management component 524 may further check a UE location constraint. The UE location constraint may refer to a given location for the UE 804-l, 806-m relative to a standby cell. In other words, the centralized energy management component 524 may check whether the UE 804-l, 806-m is within a radio transmission range for the standby cell. The centralized energy management component 524 may receive an energy saving decision parameter 210-4 and an energy saving input value 212-4 to check a UE location constraint.

In the operating environment 900, for example, the UE 804-1 may be at an edge of a transmission envelope for the UMTS cell 820-1, which is just outside a transmission envelope of the GSM cell 810-1. In this case, the UMTS cell 820-1 cannot enter an activated energy saving state 302 since the UE location constraint for the energy saving decision algorithm is FALSE. However, if the UE 804-1 were to move within the transmission envelope of the GSM cell 810-1, and all other energy saving conditions are TRUE, the centralized energy management component 524 may issue an activate energy control directive 230-1 to a power management component 714 of one or more base stations of the UMTS cell 820-1 to enter an activated energy saving state 302.

FIG. 10 illustrates an embodiment of an operating environment 1000. The operating environment 1000 illustrates an exemplary use scenario for the centralized energy management component 524 utilizing an energy saving decision algorithm with multiple decision factors, including an exemplary UE capability constraint and/or an exemplary UE location constraint for one or more macro cells.

As shown in FIG. 10, the operating environment 1000 illustrates multiple over-lapping cells for different interoperable RAT networks 1012, 1014 and 1016. The RAT network 1012 may locate certain equipment, such as an RF transceiver of a base station, on a cellular tower 1050 to form a macro cell 1002. The RAT network 1014 may comprise smaller micro cells 1004-1, 1004-2. The RAT network 1016 may comprise an even smaller pico cell 1006. The micro cells 1004-1, 1004-2 and the pico cell 1006 may each be fully enveloped by a transmission envelope for the macro cell 1002.

In this use scenario, the macro cell 1002 of the RAT network 1012 may provide basic coverage, while the micro cells 1004-1, 1004-2 and the pico cell 1006 are used to boost network capacity for coping with higher traffic loads, such as during peak hours. Assuming the RAT networks 1012, 1014 and 1016 have some measure of interoperability, the centralized energy management component 524 may use the three or four decision factors discussed with reference to FIGS. 8, 9 to determine whether to place the micro cells 1004-1, 1004-2 and/or the pico cell 1006 in an activated energy saving state 302 or a deactivated energy saving state 304 based on testing results for these decision factors.

FIG. 11 illustrates an embodiment of an operating environment 1100. The operating environment 1100 illustrates an exemplary use scenario for the centralized energy management component 524 utilizing an energy saving decision algorithm with multiple decision factors, including an exemplary UE capability constraint and/or an exemplary UE location constraint for one or more macro cells, micro cells and pico cells.

As shown in FIG. 11, the operating environment 1100 illustrates multiple over-lapping cells for different interoperable RAT networks 1112, 1114 and 1116. The RAT network 1112 may locate certain equipment, such as an RF transceiver of a base station, on a cellular tower 1150 to form a macro cell 1102-1. The RAT network 1112 may locate certain equipment, such as an RF transceiver of a base station, on a cellular tower 1160 to form a macro cell 1102-2. The RAT network 1116 may comprise smaller micro cells 1006-1, 1006-2 and 1006-3. The micro cells 1106-1, 1106-3 may each be fully enveloped by a corresponding transmission envelope for each of the macro cells 1102, 1104, respectively. The micro cell 1106-2, however, may be fully enveloped by both transmission envelopes of the macro cells 1102, 1104.

In this use scenario, the macro cells 1102, 1104 of the RAT networks 1112, 1114 may provide basic coverage, while the micro cells 1106-1, 1106-2 and 1106-3 are used to boost network capacity for coping with higher traffic loads, such as during peak hours. Assuming the RAT networks 1112, 1114 and 1116 have some measure of interoperability, the centralized energy management component 524 may use the three or four decision factors discussed with reference to FIGS. 8-10 to determine whether to place the micro cells 1106-1, 1106-2 and 1006-3 in an activated energy saving state 302 or a deactivated energy saving state 304 based on testing results for these decision factors.

Operations for the above-described embodiments may be further described with reference to one or more logic flows. It may be appreciated that the representative logic flows do not necessarily have to be executed in the order presented, or in any particular order, unless otherwise indicated. Moreover, various activities described with respect to the logic flows can be executed in serial or parallel fashion. The logic flows may be implemented using one or more hardware elements and/or software elements of the described embodiments or alternative elements as desired for a given set of design and performance constraints. For example, the logic flows may be implemented as logic (e.g., computer program instructions) for execution by a logic device (e.g., a general-purpose or specific-purpose computer).

FIG. 12 illustrates one embodiment of a logic flow 1200. The logic flow 1200 may be representative of some or all of the operations executed by one or more embodiments described herein, such as the distributed energy management component 222 or the centralized energy management component 524 of the energy management application 220.

In the illustrated embodiment shown in FIG. 12, the logic flow 1200 may receive one or more energy saving decision parameters from a network resource profile associated with a network resource of a RAT network at block 1202. For example, the energy management application 220 may receive one or more energy saving decision parameters 210-e from a network resource profile 208 associated with a network resource of a RAT network 102, 112. Examples of a network resource may comprise the base stations 104-a, 114-c, such as the exemplary base station 104-1 and/or the base station platform components 402-i, among others.

The logic flow 1200 may determine whether to switch the network resource to one of multiple energy saving states based on the one or more energy saving decision parameters at block 1204. For example, the energy management application 220 may determine whether to switch the network resource to one of multiple energy saving states 302, 304 based on the one or more energy saving decision parameters 210-e. The energy management application 220 may receive one or more energy saving input values 212-f, compare the received energy saving input values 212-f with corresponding energy saving decision parameters 210-e, and determine whether to switch the network resource to one of multiple energy saving states 302, 304 based on the comparison results.

The logic flow 1200 may send an energy control directive to instruct the network resource to switch energy saving states at block 1206. For example, the energy management application 220 may send an energy control directive 230-g to instruct the network resource to switch energy saving states 302, 304 based on comparison results. The energy management application 220 may send a handoff control directive 240-h to handoff UE 106-b, 116-d from the RAT network 102 to a standby RAT network 112 prior to sending an energy control directive 230-g to instruct the network resource to switch energy saving states.

FIG. 13 illustrates an embodiment of a logic flow 1300. The logic flow 1300 may be representative of some or all of the operations executed by one or more embodiments described herein, such as an energy savings decision algorithm implemented for the distributed energy management component 222 or the centralized energy management component 524 of the energy management application 220. As indicated by the logic flow 1300, an energy control directive 230-g may be issued after no decision factors have been evaluated, a single decision factor has been evaluated, or some combination of multiple different decision factors have been evaluated, as desired for a given implementation. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 13, the logic flow 1300 may check a traffic load value at block 1302. For instance, an energy saving decision algorithm for the energy management application 220 may check a traffic load constraint by receiving an energy saving input value 212-1 comprising a traffic load value for the RAT network 112 over a defined time period (e.g., minutes, hours, etc.). The energy saving decision algorithm may compare the traffic load value with an energy saving decision parameter 210-1 comprising a threshold value. The energy saving decision algorithm may send an activate energy control directive 230-1 when the traffic load value is less than the threshold value, or a deactivate energy control directive 230-2 when the traffic load value is greater than the threshold value.

The logic flow 1300 may check a standby RAT network value representing a standby RAT network at block 1304. For example, the energy saving decision algorithm may check a standby network constraint by receiving an energy saving input value 212-2 comprising a standby RAT network value representing a standby RAT network 102 for the RAT network 112. The energy saving decision algorithm may compare the standby RAT network value with an energy saving decision parameter 210-2 comprising suitable standby networks compatible with the RAT network 112. The energy saving decision algorithm may send an activate energy control directive 230-1 when the standby RAT network value and the energy saving decision parameter 210-2 match, or a deactivate energy control directive 230-2 when the standby RAT network value and the energy saving decision parameter 210-2 do not match.

The logic flow 1300 may check a capability value representing a RAT network operable with a set of UE at block 1306. For example, the energy saving decision algorithm may check a UE capability constraint by receiving an energy saving input value 212-3 comprising a capability value representing alternate RAT networks with which the UE 116-d may operate. The energy saving decision algorithm may compare the capability value with an energy saving decision parameter 210-3 comprising a type of network implemented by the standby network value. The energy saving decision algorithm may send an activate energy control directive 230-1 when the capability value (e.g., a GSM device) and the network type implemented by the standby network (e.g., a GSM network) match, or a deactivate energy control directive 230-2 when there is no match.

The logic flow 1300 may check a communication value representing a communication state of a set of UE at block 1308. For example, the energy saving decision algorithm may check a UE location constraint by receiving an energy saving input value 212-4 comprising a communication value representing a communication state of the UE 116-d. For instance, the communication value may comprise a binary value (e.g., 1 or 0) corresponding to whether a UE 116-1 may communicate (e.g., TRUE) or may not communication (e.g., FALSE) with the base station 104-1 of the RAT network 102. Alternatively, the communication value may comprise a statistical measurement of some form of channel quality, such as a received signal strength indicator (RSSI) or signal-to-noise ratio (SNR), for example. The energy saving decision algorithm may compare the communication value with an energy saving decision parameter 210-4 comprising an interpretation for the communication value (e.g., 1=TRUE, 0=FALSE) or a threshold value for a given level of channel quality. The energy saving decision algorithm may send an activate energy control directive 230-1 when the communication value and the energy saving decision parameter 210-4 match, or a deactivate energy control directive 230-2 when there is no match.

It may be appreciated that an energy saving decision algorithm may evaluate additional or alternative decision factors as encoded in the energy saving decision parameters 210-e. For instance, an energy saving decision algorithm may use a time of day corresponding to peak and non-peak hours, certain dates corresponding to network outages or upgrades, network operator preferences, energy saving target values, and so forth. The embodiments are not limited to a number or type of decision factors implemented by a given energy saving decision algorithm for the energy management application 220.

FIG. 14 illustrates an embodiment of an exemplary computing architecture 1400 suitable for implementing various embodiments as previously described. As used in this application, the terms “system” and “device” and “component” are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing architecture 1400. For example, a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Further, components may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

In one embodiment, the computing architecture 1400 may comprise or be implemented as part of an electronic device. Examples of an electronic device may include without limitation a mobile device, a personal digital assistant, a mobile computing device, a smart phone, a cellular telephone, a handset, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a handheld computer, a tablet computer, a server, a server array or server farm, a web server, a network server, an Internet server, a work station, a mini-computer, a main frame computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, television, digital television, set top box, wireless access point, base station, subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. The embodiments are not limited in this context.

The computing architecture 1400 includes various common computing elements, such as one or more processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components, and so forth. The embodiments, however, are not limited to implementation by the computing architecture 1400.

As shown in FIG. 14, the computing architecture 1400 comprises a processing unit 1404, a system memory 1406 and a system bus 1408. The processing unit 1404 can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures may also be employed as the processing unit 1404. The system bus 1408 provides an interface for system components including, but not limited to, the system memory 1406 to the processing unit 1404. The system bus 1408 can be any of several types of bus structure that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures.

The computing architecture 1400 may comprise or implement various articles of manufacture. An article of manufacture may comprise a computer-readable storage medium to store various forms of programming logic. Examples of a computer-readable storage medium may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of programming logic may include executable computer program instructions implemented using any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like.

The system memory 1406 may include various types of computer-readable storage media in the form of one or more higher speed memory units, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, or any other type of media suitable for storing information. In the illustrated embodiment shown in FIG. 14, the system memory 1406 can include non-volatile memory 1410 and/or volatile memory 1412. A basic input/output system (BIOS) can be stored in the non-volatile memory 1410.

The computer 1402 may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal hard disk drive (HDD) 1414, a magnetic floppy disk drive (FDD) 1416 to read from or write to a removable magnetic disk 1418, and an optical disk drive 1420 to read from or write to a removable optical disk 1422 (e.g., a CD-ROM or DVD). The HDD 1414, FDD 1416 and optical disk drive 1420 can be connected to the system bus 1408 by a HDD interface 1424, an FDD interface 1426 and an optical drive interface 1428, respectively. The HDD interface 1424 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE 1494 interface technologies.

The drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For example, a number of program modules can be stored in the drives and memory units 1410, 1412, including an operating system 1430, one or more application programs 1432, other program modules 1434, and program data 1436.

A user can enter commands and information into the computer 1402 through one or more wire/wireless input devices, for example, a keyboard 1438 and a pointing device, such as a mouse 1440. Other input devices may include a microphone, an infra-red (IR) remote control, a joystick, a game pad, a stylus pen, touch screen, or the like. These and other input devices are often connected to the processing unit 1404 through an input device interface 1442 that is coupled to the system bus 1408, but can be connected by other interfaces such as a parallel port, IEEE 1494 serial port, a game port, a USB port, an IR interface, and so forth.

A monitor 1444 or other type of display device is also connected to the system bus 1408 via an interface, such as a video adaptor 1446. In addition to the monitor 1444, a computer typically includes other peripheral output devices, such as speakers, printers, and so forth.

The computer 1402 may operate in a networked environment using logical connections via wire and/or wireless communications to one or more remote computers, such as a remote computer 1448. The remote computer 1448 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer 1402, although, for purposes of brevity, only a memory/storage device 1450 is illustrated. The logical connections depicted include wire/wireless connectivity to a local area network (LAN) 1452 and/or larger networks, for example, a wide area network (WAN) 1454. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network, for example, the Internet.

When used in a LAN networking environment, the computer 1402 is connected to the LAN 1452 through a wire and/or wireless communication network interface or adaptor 1456. The adaptor 1456 can facilitate wire and/or wireless communications to the LAN 1452, which may also include a wireless access point disposed thereon for communicating with the wireless functionality of the adaptor 1456.

When used in a WAN networking environment, the computer 1402 can include a modem 1458, or is connected to a communications server on the WAN 1454, or has other means for establishing communications over the WAN 1454, such as by way of the Internet. The modem 1458, which can be internal or external and a wire and/or wireless device, connects to the system bus 1408 via the input device interface 1442. In a networked environment, program modules depicted relative to the computer 1402, or portions thereof, can be stored in the remote memory/storage device 1450. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

The computer 1402 is operable to communicate with wire and wireless devices or entities using the IEEE 802 family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE 802.11 over-the-air modulation techniques) with, for example, a printer, scanner, desktop and/or portable computer, personal digital assistant (PDA), communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices. Wi-Fi networks use radio technologies called IEEE 802.11x (a, b, g, n, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE 802.3-related media and functions).

Various embodiments may be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, components, processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given implementation.

Some embodiments may comprise an article of manufacture. An article of manufacture may comprise a storage medium to store logic. Examples of a storage medium may include one or more types of computer-readable storage media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of the logic may include various software elements, such as software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. In one embodiment, for example, an article of manufacture may store executable computer program instructions that, when executed by a computer, cause the computer to perform methods and/or operations in accordance with the described embodiments. The executable computer program instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The executable computer program instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a computer to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.

Some embodiments may be described using the expression “one embodiment” or “an embodiment” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.

Some embodiments may be described using the expression “coupled” and “connected” along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, some embodiments may be described using the terms “connected” and/or “coupled” to indicate that two or more elements are in direct physical or electrical contact with each other. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

It is emphasized that the Abstract of the Disclosure is provided to comply with 37 C.F.R. Section 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein,” respectively. Moreover, the terms “first,” “second,” “third,” and so forth, are used merely as labels, and are not intended to impose numerical requirements on their objects.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. 

1. An apparatus, comprising: a processor circuit; and an energy management application operative on the processor circuit to manage energy consumption for one or more radio access technology (RAT) networks, the energy management application comprising a distributed energy management component operative to manage energy saving states for one or more network resources of a single RAT network, the distributed energy management component to receive one or more energy saving decision parameters from a network resource profile associated with a network resource of the single RAT network, determine whether to switch the network resource to one of multiple energy saving states based on the one or more energy saving decision parameters, and send an energy control directive to instruct the network resource to switch energy saving states.
 2. The apparatus of claim 1, the distributed energy management component to receive one or more energy saving input values, compare the received energy saving input values with corresponding energy saving decision parameters, and determine whether to switch the network resource to one of multiple energy saving states based on the comparison results.
 3. The apparatus of claim 1, the energy saving decision parameters comprising stored defined values for traffic load information, communication status information, channel status information, channel quality information (CQI), quality of service class indicator (QCI), signal-to-noise ratio (SNR), signal-to-interference ratio (SIR), signal-to-noise plus interference (SNIR), signal-to-noise and distortion ratio (SINAD), carrier-to-noise ratio (CNR), normalized signal-to-noise ratio (E_(b)/N₀), bit error rate (BER), packet error rate (PER), time information, date information, power consumption information, user equipment information, or standby RAT network information.
 4. The apparatus of claim 1, the energy saving input values comprising real-time values for traffic load information, communication status information, channel status information, channel quality information (CQI), quality of service class indicator (QCI), signal-to-noise ratio (SNR), signal-to-interference ratio (SIR), signal-to-noise plus interference (SNIR), signal-to-noise and distortion ratio (SINAD), carrier-to-noise ratio (CNR), normalized signal-to-noise ratio (E_(b)/N₀), bit error rate (BER), packet error rate (PER), time information, date information, power consumption information, user equipment information, or standby RAT network information.
 5. The apparatus of claim 1, the energy saving state comprising an activated energy saving state where the network resource is non-operational or a deactivated energy saving state where the network resource is operational.
 6. The apparatus of claim 1, the energy control directive comprising an activate energy control directive to instruct the network resource to switch from a deactivated energy saving state to an activated energy saving state, or a deactivate energy control directive to instruct the network resource to switch from the activated energy saving state to the deactivated energy saving state.
 7. The apparatus of claim 1, the processor circuit and the energy management application comprising part of a base station of a RAT network.
 8. The apparatus of claim 1, the network resource comprising a base station platform component for a base station of the RAT network.
 9. The apparatus of claim 1, the network resource comprising a base station platform component for a base station of the RAT network, the base station platform component comprising a power supply, a radio frequency (RF) transceiver, or an antenna array.
 10. The apparatus of claim 1, the distributed energy management component operative to send a handoff control directive to handoff user equipment from the single RAT network to a standby RAT network prior to sending an energy control directive to instruct the network resource to switch energy saving states.
 11. The apparatus of claim 1, the distributed energy management component operative to receive an energy saving input value comprising a traffic load value for the RAT network over a defined time period, compare the traffic load value with an energy saving decision parameter comprising a threshold value, and send an activate energy control directive when the traffic load value is less than the threshold value, and a deactivate energy control directive when the traffic load value is greater than the threshold value.
 12. The apparatus of claim 1, the distributed energy management component operative to receive an energy saving input value comprising a standby RAT network value representing a standby RAT network for the single RAT network.
 13. The apparatus of claim 12, the distributed energy management component operative to receive an energy saving input value comprising a capability value representing an alternate RAT network for the single RAT network that is compatible with user equipment.
 14. The apparatus of claim 13, the distributed energy management component operative to compare the standby RAT network value with the capability value.
 15. The apparatus of claim 14, the distributed energy management component operative to send an activate energy control directive when the standby RAT network value matches the capability value, and a deactivate energy control directive when the standby RAT network value does not match the capability value.
 16. The apparatus of claim 14, the distributed energy management component operative to receive an energy saving input value comprising a communication value representing a communication state of the user equipment when the standby RAT network value matches the capability value, and send an activate energy control directive when the communication value indicates an active communication state between the user equipment and the standby RAT network, and a deactivate energy control directive when the communication value indicates a deactive communication state between the user equipment and the standby RAT network.
 17. An apparatus, comprising: a processor circuit; and an energy management application operative on the processor circuit to manage energy consumption for one or more radio access technology (RAT) networks, the energy management application comprising a centralized energy management component operative to manage energy saving states for one or more network resources of multiple interoperable RAT networks, the centralized energy management component to retrieve an energy saving schedule for network resources of the multiple interoperable RAT networks, and according to the energy saving schedule, receive one or more energy saving decision parameters from a network resource profile associated with a network resource of a single RAT network, determine whether to switch the network resource to one of multiple energy saving states based on the one or more energy saving decision parameters, and send an energy control directive to instruct the network resource to switch energy saving states.
 18. The apparatus of claim 17, the energy saving state comprising an activated energy saving state where the network resource is non-operational or a deactivated energy saving state where the network resource is operational.
 19. The apparatus of claim 17, the energy control directive comprising an activate energy control directive to instruct the network resource to switch from a deactivated energy saving state to an activated energy saving state, or a deactivate energy control directive to instruct the network resource to switch from the activated energy saving state to the deactivated energy saving state.
 20. The apparatus of claim 17, the processor circuit and the energy management application comprising part of an operation, administration, maintenance (OAM) device of a RAT network.
 21. (canceled)
 22. (canceled)
 23. (canceled)
 24. (canceled)
 25. (canceled)
 26. A method, comprising: receiving one or more energy saving decision parameters from a network resource profile associated with a network resource of a radio access technology (RAT) network; determining whether to switch the network resource to one of multiple energy saving states based on the one or more energy saving decision parameters; and sending an energy control directive to instruct the network resource to switch energy saving states.
 27. The method of claim 26, comprising: receiving one or more energy saving input values; comparing the received energy saving input values with corresponding energy saving decision parameters; and determining whether to switch the network resource to one of multiple energy saving states based on the comparison results.
 28. The method of claim 26, comprising sending a handoff control directive to handoff user equipment from the single RAT network to a standby RAT network prior to sending an energy control directive to instruct the network resource to switch energy saving states.
 29. The method of claim 26, comprising: receiving an energy saving input value comprising a traffic load value for the RAT network over a defined time period; comparing the traffic load value with an energy saving decision parameter comprising a threshold value; and sending an activate energy control directive when the traffic load value is less than the threshold value, or a deactivate energy control directive when the traffic load value is greater than the threshold value.
 30. The method of claim 26, comprising: receiving an energy saving input value comprising a standby RAT network value representing a standby RAT network for the RAT network; receiving an energy saving input value comprising a capability value representing an alternate RAT network for the single RAT network that is compatible with user equipment; and comparing the standby RAT network value with the capability value.
 31. The method of claim 30, comprising sending an activate energy control directive when the standby RAT network value matches the capability value, or a deactivate energy control directive when the standby RAT network value does not match the capability value.
 32. The method of claim 30, comprising: receiving an energy saving input value comprising a communication value representing a communication state of the user equipment when the standby RAT network value matches the capability value; and sending an activate energy control directive when the communication value indicates an active communication state between the user equipment and the standby RAT network, and a deactivate energy control directive when the communication value indicates a deactive communication state between the user equipment and the standby RAT network.
 33. An article of manufacture comprising a storage medium containing instructions that when executed enable a system to: receive one or more energy saving decision parameters from a network resource profile associated with a network resource of a radio access technology (RAT) network; receive one or more energy saving input values; compare the received energy saving input values with corresponding energy saving decision parameters determine whether to switch the network resource to one of multiple energy saving states based on the comparison results; and send an energy control directive to instruct the network resource to switch energy saving states according to the determination results.
 34. The article of claim 33, further comprising instructions that when executed enable the system to: send an activate energy control directive to instruct the network resource to switch from a deactivated energy saving state to an activated energy saving state; or send a deactivate energy control directive to instruct the network resource to switch from the activated energy saving state to the deactivated energy saving state.
 35. The article of claim 33, further comprising instructions that when executed enable the system to send a handoff control directive to handoff user equipment from the RAT network to a standby RAT network prior to sending an energy control directive to instruct the network resource to switch energy saving states. 